Hmm iirc there were restrictions that applied to current keyword army overloads but not to @:overload, which means unless we update "proper" overloads we'll be removing some features there (not yet since it's only a deprecation warning, but still).

I found #10611 which might be a bit niche since it doesn't apply to all targets, but maybe those targets still need something (@:js.overload(...) ?)

Not sure if there was more

I'm pretty sure that both syntaxes should behave the same way and if there's a difference then that's just some inconsistency.